Lot of questions over here, this is a new world for me:

• Not sure which criteria do we use to bump the version here but may be a good opportunity to do it? 🤔
• In the description the babel-plugin-macros is listed as added, is it actually?

And I would also like to bring up this comment in the original issue: #567 (comment)

Ah. I see the problem. Our lead developer is requiring individual plugins from @babel/preset-env in the process of specifying the babel configuration.
This appears to be the issues he is trying to resolve:
Though the "loose" option was set to "false" in your @babel/preset-env config, it will not be used for @babel/plugin-proposal-private-property-in-object since the "loose" mode option was set to "true" for @babel/plugin-proposal-private-methods.
Is it possible to make Codeclimate not choke when individual plugins are required that are included in @babel/preset-env?

Is this issue solved just by adding the plugin-proposal-private-methods ? According to the official docs it's already included on @babel/preset-env, which is the benefit of adding it explicitly? Don't we need to specify the loose option?

• wouldn't using the include option in preset-env have the same effect?

Sorry if there are too many questions!

Lot of questions over here, this is a new world for me:
...

@camillof I added babel-plugin-macros and it looks like another plugin was suggested in place for the other ones I added here, so I'll analyze adding babel-plugin-transform-react-remove-prop-types.

Regarding the "loose" warning, it looks like it's solved by adding only plugin-proposal-private-methods like you're saying, so I'll be trying that out

Closing this in favor of #579